docs(release): SVN revision in vote email + personal-email vote resolution#903
Merged
Merged
Conversation
…ution Two follow-ups from the 0.1.0 release vote thread: - release-vote-draft: include the staged SVN revision in the [VOTE] email body for the svnpubsub backend, so voters can pin exactly which artefacts they reviewed (SVN branches are mutable). Requested by Sebb. - pmc-roster: allow the Primary email cell to list several comma-separated addresses so a PMC member voting from a personal address resolves as binding; add jarek@potiuk.com to the chair row. Raised by the 0.1.0 vote.
release-promote now emits a Step 3 of 3 that cuts the final GPG-signed <version> tag on the same commit as the approved RC (no rebuild) and pushes it, so downstream links (changelog, [ANNOUNCE], site) reference the final tag rather than <version>-rcN. Adds the rc_commit_sha, rm_gpg_fingerprint, and git_upstream_remote metadata rows it needs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three follow-ups from the Apache Magpie 0.1.0 release vote thread on dev@:
[VOTE]email body (svnpubsub backend). SVN branches are mutable, so the revision
pins exactly which artefacts each voter reviewed. Raised by Sebb.
Primary emailcell may now list severalcomma-separated addresses, so a PMC member who votes from a personal
address resolves as binding. Adds
jarek@potiuk.comto the chair row.pushes the GPG-signed
<version>tag on the same commit as the approvedRC, so changelog / [ANNOUNCE] / site links reference the final tag, not
<version>-rcN. Surfaced by the 0.1.0 release.Documentation/config changes to the release tooling only; no code paths affected.